Integration of emergency alert information

ABSTRACT

A subscriber of the Emergency Alert System (EAS) receiving an EAS alert message can obtain additional multimedia information in based upon the location of the subscriber. The additional multimedia information can include information pertaining to available shelter, medical facilities, the location of emergency supplies, a plume map, evacuation routes, or the like. In an example embodiment, the Global Positioning System or other device location systems is utilized to determine the location of the subscriber. The location information along with EAS alert information is used to query a database to obtain the additional information.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to, and is a continuation of, U.S.application Ser. No. 13/465,449 filed on May 7, 2012, which is acontinuation of U.S. application Ser. No. 12/056,115, now U.S. Pat. No.8,190,118, filed on Mar. 26, 2008, both of which are entitled“Integration Of Emergency Alert Information,” and which are herebyincorporated by reference in their entirety. This application is relatedby subject matter to U.S. patent application Ser. No. 11/624,503,entitled “EMERGENCY ALERT INFORMATION BASED UPON SUBSCRIBER LOCATION,”filed Jan. 18, 2007, and U.S. patent application Ser. No. 11/532,299,entitled “BROADCAST INITIATED RETRIEVAL OF MULTIMEDIA ASSOCIATED WITH ANALERT,” filed Sep. 15, 2006, both of which are hereby incorporated byreference in their entirety.

TECHNICAL FIELD

The technical field generally relates to communications systems and morespecifically relates to providing alert information via the EmergencyAlert System (EAS) in accordance with a location of a subscriber of theEAS.

BACKGROUND

The Emergency Alert System (EAS) is capable of providing messagesindicative of a variety of types of alerts. Via the EAS, subscribersthereof can receive messages pertaining to weather conditions,disasters, AMBER (America's Missing: Broadcast Emergency Response)alerts, and/or alerts issued by the Government, for example. A problem,however, is that a recipient of an EAS message may not know how toproceed. For example, a subscriber may receive an EAS message indicatingthat a tornado is highly likely to occur. The subscriber, however, maynot know where available shelter is located. Even worse, in an attemptto flee the area, a subscriber could head into the path of the tornado.

SUMMARY

Emergency Alert System (EAS) information is provided in accordance witha location of an EAS subscriber. The location of the subscriber isutilized to provide, along with the EAS alert message, informationpertaining to, for example, available shelter, medical facilities,location of emergency supplies, plume maps, evacuation routes, or thelike. In an example embodiment, the Global Positioning System and/orCellular location technology is utilized to determine the location ofthe subscriber. The location information along with EAS alertinformation is used to query a database to obtain information to beprovided to the subscriber. The obtained information is provided to thesubscriber along with the EAS alert message.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, aspects and advantages of EmergencyAlert System (EAS) emergency alert information based upon subscriberlocation will be better understood from the following detaileddescription with reference to the drawings.

FIG. 1 is a flow diagram of an example system and process for providingEAS emergency alert information based upon subscriber location.

FIG. 2 is flow diagram of an example process and system for retrievingmultimedia associated with an alert in response to a broadcast of thealert.

FIG. 3 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichthe system for distributing emergency alert information based onsubscriber location can be practiced.

FIG. 4 illustrates an architecture of a typical GPRS network assegmented into four groups.

FIG. 5 illustrates an example alternate block diagram of an exemplaryGSM/GPRS/IP multimedia network architecture in which distributingemergency alert information based on subscriber location can beaccomplished.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

In accordance with one embodiment of the invention, information providedto a recipient of emergency information from an Emergency Alert System(EAS) takes the recipient's location into account. For example, if anemergency event is related to a gas leak or the like, the recipient canbe provided a plume map and/or information pertaining to the plume mapindicating the current and/or projected area of coverage of the gas.Based upon the recipient's current location, the information can containa variety of useful information, such as an evacuation route, locationsof shelters, locations of medical facilities, locations of medicalsupplies, locations of other support facilities, phone numbers, emailaddresses, or the like.

FIG. 1 is a flow diagram of an example system and process for providingEAS information in accordance with the current location of an EASrecipient. In the embodiment of FIG. 1, it is contemplated that therecipient is a person carrying a mobile device, and that the EASinformation is provided to the mobile device. In such embodiments, therecipient may be referred to as a “subscriber.” The term subscriberrefers to a subscriber to a mobile communications agreement, such as acellular telephone contract, and/or a subscriber to an EAS informationservice. At step 12, the emergency alert server 58 receives, from theemergency alert network 62, an indication of an emergency alertassociated with an alerting area. The alerting area can comprise anyappropriate area, such as a geographical area, a group of subscribers,or a combination thereof for example. For example, an alert area can bedefined in accordance with geographic code references such as theFederal Information Processing Standard (FIPS), ZIP codes, the NationalWeather Service Specific Area Message Encoding (SAME) codes, and/or theGeographic Information System (GIS) Alert Mapping Service. An alert areacan comprise a group of subscribers, such as, for example, a group ofsubscribers belonging to the same organization (e.g., group ofsubscribers employed at a medical facility).

At step 14, the emergency alert server 58 provides, to the emergencyalert delivery network 54, the indication of the emergency alert and theassociated alert area. As described in more detail below, the emergencyalert delivery network 54 can comprise any appropriate network, such asa wired network and/or a wireless network, for example. In an exampleembodiment the emergency alert delivery network comprises a ShortMessage Service (SMS) network, Cell Broadcast network, a MultimediaBroadcast/Multicast Service (“MBMS”), and/or video broadcast network,such as Digital Video broadcast-Handheld (“DVB-H”), an IP Multicastnetwork, and MediaFLO network, an FM radio network, a NationalOceanographic and Atmospheric Administration (NOAA) National WeatherService Radio All Hazards (NWR) network, and a Mobile TV network, orcombination thereof). The emergency alert delivery network 54 provides,at step 16, the indication of the emergency alert and the associatedalert area to the wireless network 52. As described in more detailbelow, the emergency alert deliver network can comprise any appropriatenetwork, such as a wired network and/or a wireless network, for example.In an example embodiment, as described in more detail below, thewireless network 52 comprises a Global System for Mobile Communications(GSM) network, a Universal Mobile Telecommunications System (UMTS)network, a Code Division Multiple Access (CDMA) network, a CDMA-2000network, an Integrated Digital Enhanced Network (iDEN) network, a WiFinetwork, a Worldwide Interoperability for Microwave Access (WiMAX)network, or a combination thereof).

At step 18, the wireless network 52 provides, to the devices 50 withinthe alert area, the indication of the emergency alert. The devices 50are representative of any appropriate type of device, or devices, thatcan be utilized to receive the indication of the emergency alert fromthe wireless network 52. The devices 50 can represent a mobile device.Example mobile devices include any type of wireless receiver ortransceiver device with broadcast reception capabilities (e.g., cellphone, pager, PDA, PC, specialized broadcast receiving device, firstresponder Mobile Data Terminal (MDT), FM/AM radio, NOAA weather radio,Land Mobile Radio (LMR), satellite radio receiver, satellite phone, andtelevision). The devices 50 also can represent non-mobile devices, suchas devices fixed in homes to receive the alerts.

The devices 50 can comprise any combination of any type of wirelessreceiver or transceiver device with broadcast reception capabilities(e.g., cell phone, pager, PDA, PC, specialized broadcast receivingdevice, first responder Mobile Data Terminal (MDT), FM/AM radio, NOAAweather radio, Land Mobile Radio (LMR), satellite radio receiver,satellite phone, and television). Example devices can comprise anyappropriate mobile device, such as, for example, a portable device, avariety of computing devices including (a) a portable media player,e.g., a portable music player, such as an MP3 player, a walkmans, etc.,(b) a portable computing device, such as a laptop, a personal digitalassistant (“PDA”), a portable phone, such as a cell phone of the like, asmart phone, a Session Initiation Protocol (SIP) phone, a video phone, aportable email device, a thin client, a portable gaming device, etc.,(c) consumer electronic devices, such as TVs, DVD players, set topboxes, monitors, displays, etc., (d) a public computing device, such asa kiosk, an in-store music sampling device, an automated teller machine(ATM), a cash register, etc., (e) a navigation device whether portableor installed in-vehicle and/or (f) a non-conventional computing device,such as a kitchen appliance, a motor vehicle control (e.g., steeringwheel), etc., or a combination thereof.

The devices 50 receives, at step 20, information pertaining to thelocation of the devices 50. As depicted in FIG. 1, location informationis received from a satellite, or satellites, such as a GlobalPositioning System (GPS). Location information can be received from anyappropriate source and in accordance with any appropriate locationdetermination technique. The location information can be received inresponse to receiving (at step 18) the indication of the emergency alertand/or the location information can be previously stored in the devices50. The location information can be automatically obtained (e.g., inresponse to receiving, at step 18, the indication of the emergencyalert) and/or the location information can be obtained manually by auser of the devices 50. For example, in response to receiving theindication of the emergency alert at step 18, the devices 50 canautomatically obtain the location of the devices 50. The locationinformation can be obtained from memory in the devices 50 and/or from asource external to the devices 50, such as from a GPS satellite, orsatellites, or by mobile device location techniques presently in use,which involve triangulating a mobile device location from signalsreceived at cellular radio communications towers. The location of thedevices 50 can be represented in any appropriate format, such as a ZIPcode, latitude and longitude, or the like, for example. It is tounderstood that the phrases “location of the subscriber,” “location ofthe device,” and location of the devices,” are used interchangeably tomean location of the intended recipient, or recipients, of additionalinformation.

Additional information is requested by the devices 50, at step 22. Theadditional information can be automatically requested by the devices 50in response to receiving location information (at step 20) and/or theadditional information can be requested manually by the user of thedevices 50. The request for additional information includes anindication of the location information. In an example embodiment, therequest for information comprises information indicative of the type ofemergency and/or information indicative of the type of subscriber (e.g.,the user of the devices 50 that is subscribed to the EAS). Informationindicative of the type of subscriber can comprise, for example, anindication that the subscriber is or is not a member of the nationalsecurity community and/or a member of the emergency preparednesscommunity (NS/EP personnel). Non-NS/EP personnel could receive locationspecific information such as evacuation routes, locations of shelters,and locations of medical facilities. NS/EP personnel could alertspecific information such as location of the event, movement of anyhazardous materials (e.g., speed and direction of toxic clouds), andinformation that would not be provided to the general public, such asspecific detailed information about the hazardous materials (e.g.,Material Safety Data Sheet “MSDS”), mortality rates in the alertingareas, prognosis of victims exposed to the hazard, or the like. Thus, inan example embodiment, the request for additional information comprisesan indication of the location of the devices 50 and/or an indication ofthe alert area, an indication of the type of subscriber, and anindication of the type of emergency. The wireless network 52 provides,at step 24, to the wireless data network 56, the request for additionalinformation. At step 26, the wireless data network 56 provides, to theemergency alert server 58, the request for additional information.

At step 28, the emergency alert server 58 provides, to the serverlocation database 60, a request for additional information. The serverlocation database 60 can comprise any appropriate database or group ofdatabases. In an example embodiment, the emergency alert server 58queries the server location database 60 utilizing the indication of thelocation of the devices 50 and/or an indication of the alert area, theindication of the type of subscriber, and the indication of the type ofemergency. The emergency alert server 58 queries the server locationdatabase 60 to determine the location, such a URL or other appropriateroutable address, of a supplemental emergency alert information server.In response to the query, the server locations database 60 determines alocation or locations, such as a URL or other routable address (e.g., IPaddress) of an appropriate supplemental emergency alert informationserver. The server location database 60 provides, at step 30, to theemergency alert server 58, the location or locations, of an appropriatesupplemental emergency alert information server (e.g., supplementalemergency alert information server 66).

At step 32, the emergency alert server 58 provides to the internetand/or intranet 64, a request for additional information. The request isprovided, via the internet/intranet 64, to the location or locations, ofthe supplemental emergency alert information server 66 as determined bythe server location database 60. If not already established, theemergency alert server 58 establishes a connection with theinternet/intranet 64 prior to providing the request for additionalinformation to the internet/intranet 64. At step 34, theinternet/intranet 64 provides, to the supplemental emergency alertinformation server 66, the request for additional information. In anexample embodiment, the request for information comprises the indicationof the location of the devices 50 and/or an indication of the alertarea, the indication of the type of subscriber, and the indication ofthe type of emergency.

Utilizing the indication of the location of the devices 50 and/or anindication of the alert area, the indication of the type of subscriber,and the indication of the type of emergency, the supplemental emergencyalert information server 66 obtains appropriate additional information.The supplemental emergency alert information server 66 can obtain theadditional information from any appropriate source, such as storage inthe supplemental emergency alert information server 66 and/or storageexternal to the supplemental emergency alert information server 66. Thesupplemental emergency alert information server 66 also can generateadditional information in accordance with information provided thereto(e.g., the location of a mobile device and/or an indication of the alertarea, an indication of the type of subscriber, an indication of the typeof emergency). The additional information can comprise any appropriatecontent based on the location of the subscriber/subscriber's device. Forexample, the content of the additional information can includeinformation pertaining to available shelter, medical facilities,location of emergency supplies, plume maps, evacuation routes, othersupport facilities, phone numbers, email addresses, or a combinationthereof.

At step 36, the supplemental emergency alert information server 66provides, to the internet/intranet 64, the additional information. Atstep 38, the internet/intranet 64 provides, to the emergency alertserver 58, the additional information. The emergency alert server 58, atstep 40 provides, to the wireless data network 56, the additionalinformation. At step 42, the wireless data network 56 provides, to thewireless network 52, the additional information for distribution to thedevices 50 at step 46.

Each of the emergency alert server 58 and the supplemental emergencyalert server 66 can comprise any appropriate type of processor. Theemergency alert server 58 and the supplemental emergency alert server 66can each be implemented in separate processors, in a single processor,or a combination thereof. Further, each processor can be implemented asa single processor or multiple processors. Multiple processors can bedistributed or centrally located. Multiple processors can communicatewirelessly, via hard wire, or a combination thereof. Examples processorsinclude mobile communications devices, mobile telephones, personaldigital assistants (PDAs), lap top computers, handheld processors, or acombination thereof. The server location database 60 can comprise anyappropriate type of database. The server location database 60 can beimplemented as a single database or multiple databases. Multipledatabases can be distributed or centrally located. Multiple databasescan communicate wirelessly, via hard wire, or a combination thereof.Further, the emergency alert server 58, the supplemental emergency alertserver 66, and the server location database 60 can be implemented in anycombination.

FIG. 2 is flow diagram of an example process and system for retrievingmultimedia associated with an alert in response to a broadcast of thealert, as may be used in combination with the above described system andprocess for providing EAS emergency alert information based uponsubscriber location. FIG. 2 provides one embodiment of multimediadelivery, wherein the content of the multimedia can be based onsubscriber location using techniques such as those described above. Inthe embodiment of FIG. 2, an alert, such as an alert message from theEmergency Alert System (EAS), is distributed via broadcast deliverymechanisms such as National Oceanic and Atmospheric Administration(NOAA) National Weather Radio, AM/FM radio broadcasts, mobile TVbroadcasts, satellite radio, and the like. In an example embodiment, thebroadcast alert triggers the retrieval of multimedia associated with thealert. Upon receipt of the broadcast alert, the type of alert isdetermined. A location of multimedia is determined in accordance withthe type of alert. For example, in the gas leak situation outlinedabove, appropriate multimedia could be an appropriate plume map overlaidon a map showing evacuation routes. If appropriate, video could beintegrated showing motion of the plume and or directing the subscriberto the evacuation routes. The multimedia is retrieved at the determinedlocation. The multimedia can be retrieved manually (e.g., by a user) orautomatically (e.g., by a device).

Multimedia can be provided according to recipient capabilities. Variousdifferent multimedia, such as text, a picture, video, and/or audio,associated with emergency alerts can advantageously depend oncapabilities of the person receiving the multimedia and/or the devicereceiving the multimedia. For example, a first responder or an emergencymanager at a disaster site or emergency situation could benefit fromreceiving multimedia information associated with a alert pertaining tothe disaster/emergency. Multimedia such as maps, graphics, video clips,audio clips, and still pictures can aid the first responder/manager inbetter assessing the situation and directing others. In this regard,different multimedia can be compiled for the first responder recipientcapability, which is a different subscriber type than that of theaverage civilian. A first multimedia may be compiled for a firstresponder, said multimedia providing directions to the emergencylocation along with appropriate data for addressing the emergency, whilea second multimedia can be compiled for the average citizen withinformation addressing common questions on a “need to know” basis andfurther providing evacuation routes and data for appropriate civilianresponse. Similarly, different multimedia can be provided to differentdevice types depending on recipient device capabilities. For example, acellular telephone with limited graphics capability can receive a simplepicture, voice recording, and/or short video, while an in-dashnavigation system can receive a longer video with more multimediainformation. Information regarding recipient capabilities, whether thoseof the person or those of the device, can be provided to appropriateservers by the device so that appropriate multimedia is returned.

FIG. 2 is a flow diagram of an example process and system for retrievingmultimedia associated with an alert in response to a broadcast of thealert. In an example embodiment, an alert message is delivered to a userdevice 222 via a broadcast network 12. The broadcast network 12 cancomprise any appropriate non-cellular broadcast network, such asNational Oceanic and Atmospheric Administration (NOAA) National WeatherRadio, AM/FM radio broadcasts, mobile TV broadcasts, satellite radio, ora combination thereof, for example. The user device 222 comprises apreprovisioned user device database 226 having stored thereinpredetermined locations from which multimedia can be retrieved, such asassociated addresses (e.g., Uniform Resource Locator, URL, addresses) ofmultimedia information based upon alert message type. A list ofassociated URL addresses for related multimedia information is generatedin accordance with the preprovisioned user device database 226. Thus, arespective location from which multimedia can be retrieved is generatedfor each alert type. The list is provided to the user, and the userselects from the list, specific multimedia information.

Prior to the occurrence of an event resulting in an alert (e.g., anemergency event), at step 234, locations, such as URL addresses formultimedia emergency alert information, are downloaded to the userdevice database 226 from an emergency URL database 224. Predeterminedlocations (e.g., URL addresses) are generated by associating arespective location from which multimedia can be retrieved for eachalert type. Thus, for each alert type, the user device database 226 hasstored therein, a URL address, or addresses, associated with the alerttype, and from which multimedia associated with the alert can beretrieved. The emergency URL database 224 can comprise any appropriatenetwork, processor, storage means, or the like, capable of storing andproviding URL addresses associated with multimedia informationpertaining to an alert. Upon the occurrence of an event, such as anemergency or the like, the broadcast network 12 broadcasts, at step 240,an indication of the emergency.

In the illustrated embodiment, the broadcast of the indication of thealert is received by the broadcast processor 228. The broadcast networkprocessor 228 determines the type of emergency, or the like, based uponthe received broadcast emergency alert message. The broadcast processor228 requests, at step 242, the list of associated URL addresses from theuser device database 226. The user device database 226 retrieves thelist of URL addresses associated with the indicated type of emergency,or the like, and returns, at step 244, the list of URL addresses to thebroadcast processor 228.

In an example embodiment, the user decides whether to retrieve themultimedia and selects which URL from which to retrieve the multimedia.In an alternate embodiment, multimedia data could be retrieved from anylocation, such as from a device hard drive that is pre-populated withmultimedia for display in certain emergency conditions. In accordancewith the illustrated embodiment, at step 246, the indication of thealert along with the indication of the location of multimedia associatedwith the alert are provided to the user interface 230. The userinterface 230 renders the alert message in textual format. The userinterface 230 also renders the locations of the multimedia. In anexample embodiment, the user interface 230 renders a link, or links, toa URL, or URLs, from which multimedia can be retrieved. If the userdecides to retrieve the multimedia, the user selects the link, or links,from which to retrieve the multimedia.

At step 248, an indication of the user's selection is provided to thedata network processor 232. The data network processor 232 establishes aconnection with the data network 220, if a connection is not currentlyestablished. At step 250, the data network processor 232 provides to thedata network 220, the URL address(es) selected by the user. The datanetwork 220, at step 252, using the selected URL address, establishes aconnection with an emergency information network 14. The data network220 establishes the connection with the location in the emergencyinformation network 14 indicated by the selected URL(s). The datanetwork 220, also at step 252, requests retrieval of the multimedialocated at the selected URL(s) in the emergency information network 14.The emergency information network 14, at step 254, provides therequested multimedia information to the data network 220. The datanetwork 220 provides the requested multimedia information to the datanetwork processor 232, at step 256. The data network processor 232provides the requested multimedia information to the user interface 230for rendering. In various embodiments, multimedia information associatedwith each selected URL can be retrieved individually, multimediainformation associated with a subset of the selected URLs can beretrieved, or multimedia information associated with all the selectedURLs can be retrieved.

In another example embodiment, the user device 222 automaticallyretrieves the multimedia information using the generated list of URLaddresses. In this embodiment, steps 240, 242, and 244 occur asdescribed above. At step 246, however, the indication of the alert,without the indication of the location of multimedia associated with thealert, is provided to the user interface 230 for rendering. Thebroadcast processor 228 extracts the list of URL addresses from theinformation provided by the user device database 226 (at step 244) andrequests the data network processor 232 to retrieve the associatedmultimedia information. At step 250, the data network processor 232provides to the data network 220, the URL address(es) extracted by thecellular network processor 228.

At this point, steps 252, 254, and 256, occur similarly as describedabove. That is, the data network 220, at step 252, using the extractedURL address, establishes a connection with an emergency informationnetwork 14. The data network 220 establishes the connection with thelocation in the emergency information network 14 indicated by theselected URL(s). The data network 220, also at step 252, requestsretrieval of the multimedia located at the extracted URL(s) in theemergency information network. 14. The emergency information network 14,at step 254, provides the requested multimedia information to the datanetwork 220. The data network 220 provides the requested multimediainformation to the data network processor 232, at step 256. The datanetwork processor 232 provides the requested multimedia information tothe user interface 230 for rendering. In various embodiments, multimediainformation associated with each selected URL can be retrievedindividually, multimedia information associated with a subset of theselected URLs can be retrieved, or multimedia information associatedwith all the selected URLs can be retrieved.

The user device 222 can comprise any appropriate user device. Forexample, the user device 222 comprise a mobile device, a portabledevice, a variety of computing devices including (a) a portable mediaplayer, e.g., a portable music player, such as an MP3 player, awalkmans, etc., (b) a portable computing device, such as a laptop, apersonal digital assistant (“PDA”), a portable phone, such as a cellphone of the like, a smart phone, a Session Initiation Protocol (SIP)phone, a video phone, a portable email device, a thin client, a portablegaming device, etc., (c) consumer electronic devices, such as TVs, DVDplayers, set top boxes, monitors, displays, etc., (d) a public computingdevice, such as a kiosk, an in-store music sampling device, an automatedteller machine (ATM), a cash register, etc., (e) a navigation devicewhether portable or installed in-vehicle and/or (f) a non-conventionalcomputing device, such as a kitchen appliance, a motor vehicle control(e.g., steering wheel), etc., or a combination thereof.

The user device 222 can comprise a system comprising an input/outputportion, a processing portion, and a memory portion. In an exampleembodiment the memory portion comprises the user device database 226and/or any memory associated with the broadcast processor 228, the datanetwork processor 232, the user interface 230, or a combination thereof,for example. The processing portion can comprise the broadcast processor228, the data network processor 232, or any appropriate portionsthereof, for example. The input/output portion can comprise anyappropriate portions of the user device database 226, the broadcastprocessor 228, and the data network processor 232, that interface withthe emergency URL database 224, the broadcast network 12, and the datanetwork 220.

It is emphasized that the diagram depicted in FIG. 2 of the user device222 is exemplary and not intended to imply a specific implementation.Thus, the user device 222 can be implemented in a single processor ormultiple processors. Multiple processors can be distributed or centrallylocated. Multiple processors can communicate wirelessly, via hard wire,or a combination thereof.

The user device 222 can be operable with any appropriate telephony radionetwork. The following description sets forth some exemplary telephonyradio networks, such as the global system for mobile communications(GSM), and non-limiting operating environments. The below-describedoperating environments should be considered non-exhaustive, however, andthus the below-described network architectures merely show howretrieving multimedia associated with an alert in response to abroadcast of the alert can be incorporated with existing networkstructures and architectures. It can be appreciated, however, thatretrieving multimedia associated with an alert in response to abroadcast of the alert can be incorporated with existing and/or futurealternative architectures for communication networks as well.

The GSM is one of the most widely utilized wireless access systems intoday's fast growing communication environment. The GSM providescircuit-switched data services to subscribers, such as mobile telephoneor computer users. The General Packet Radio Service (“GPRS”), which isan extension to GSM technology, introduces packet switching to GSMnetworks. The GPRS uses a packet-based wireless communication technologyto transfer high and low speed data and signaling in an efficientmanner. The GPRS attempts to optimize the use of network and radioresources, thus enabling the cost effective and efficient use of GSMnetwork resources for packet mode applications.

As one of ordinary skill in the art can appreciate, the exemplaryGSM/GPRS environment and services described herein also can be extendedto 3G services, such as Universal Mobile Telephone System (“UMTS”),Frequency Division Duplexing (“FDD”) and Time Division Duplexing(“TDD”), High Speed Packet Data Access (“HSPDA”), cdma2000 1x EvolutionData Optimized (“EVDO”), Code Division Multiple Access-2000 (“cdma20003x”), Time Division Synchronous Code Division Multiple Access(“TD-SCDMA”), Wideband Code Division Multiple Access (“WCDMA”), EnhancedData GSM Environment (“EDGE”), International MobileTelecommunications-2000 (“IMT-2000”), Digital Enhanced CordlessTelecommunications (“DECT”), etc., as well as to other network servicesthat become available in time. In this regard, the techniques ofretrieving multimedia associated with an alert in response to abroadcast of the alert can be applied independently of the method ofdata transport, and do not depend on any particular networkarchitecture, or underlying protocols.

The following description sets forth some exemplary telephony radionetworks and non-limiting operating environments for providing emergencyalert information based upon subscriber location. The below-describedoperating environments should be considered non-exhaustive, however, andthus the below-described network architectures merely show how providingemergency alert information based upon subscriber location may beincorporated into existing network structures and architectures. It canbe appreciated, however, that providing emergency alert informationbased upon subscriber location can be incorporated into existing and/orfuture alternative architectures for communication networks as well.

The global system for mobile communication (“GSM”) is one of the mostwidely utilized wireless access systems in today's fast growingcommunication environment. The GSM provides circuit-switched dataservices to subscribers, such as mobile telephone or computer users. TheGeneral Packet Radio Service (“GPRS”), which is an extension to GSMtechnology, introduces packet switching to GSM networks. The GPRS uses apacket-based wireless communication technology to transfer high and lowspeed data and signaling in an efficient manner. The GPRS attempts tooptimize the use of network and radio resources, thus enabling the costeffective and efficient use of GSM network resources for packet modeapplications.

As one of ordinary skill in the art can appreciate, the exemplaryGSM/GPRS environment and services described herein also can be extendedto 3G services, such as Universal Mobile Telephone System (“UMTS”),Frequency Division Duplexing (“FDD”) and Time Division Duplexing(“TDD”), High Speed Packet Data Access (“HSPDA”), cdma2000 1x EvolutionData Optimized (“EVDO”), Code Division Multiple Access-2000 (“cdma20003x”), Time Division Synchronous Code Division Multiple Access(“TD-SCDMA”), Wideband Code Division Multiple Access (“WCDMA”), EnhancedData GSM Environment (“EDGE”), International MobileTelecommunications-2000 (“IMT-2000”), Digital Enhanced CordlessTelecommunications (“DECT”), etc., as well as to other network servicesthat become available in time. In this regard, the techniques ofproviding emergency alert information based on subscriber location canbe applied independently of the method of data transport, and do notdepend on any particular network architecture, or underlying protocols.

FIG. 3 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichthe system for providing emergency alert information based on subscriberlocation can be practiced. In an example configuration, the emergencyalert delivery network 354, the wireless data network 356, the wirelessnetwork 352, the internet/intranet 364, and the emergency alert network362, individually or in any combination, are encompassed by the networkenvironment depicted in FIG. 3. In such an environment, there are aplurality of Base Station Subsystems (“BSS”) 300 (only one is shown),each of which comprises a Base Station Controller (“BSC”) 302 serving aplurality of Base Transceiver Stations (“BTS”) such as BTSs 304, 306,and 308. BTSs 304, 306, 308, etc. are the access points where users ofpacket-based mobile devices (e.g., devices 350) become connected to thewireless network. In exemplary fashion, the packet traffic originatingfrom user devices (e.g., devices 350) is transported via an over-the-airinterface to a BTS 308, and from the BTS 308 to the BSC 302. Basestation subsystems, such as BSS 300, are a part of internal frame relaynetwork 310 that can include Service GPRS Support Nodes (“SGSN”) such asSGSN 312 and 314. Each SGSN is connected to an internal packet network320 through which a SGSN 312, 314, etc. can route data packets to andfrom a plurality of gateway GPRS support nodes (GGSN) 322, 324, 326,etc. As illustrated, SGSN 314 and GGSNs 322, 324, and 326 are part ofinternal packet network 320. Gateway GPRS serving nodes 322, 324 and 326mainly provide an interface to external Internet Protocol (“IP”)networks such as Public Land Mobile Network (“PLMN”) 350, corporateintranets 340, or Fixed-End System (“FES”) or the public Internet 330.As illustrated, subscriber corporate network 340 may be connected toGGSN 324 via firewall 332; and PLMN 350 is connected to GGSN 324 viaboarder gateway router 334. The Remote Authentication Dial-In UserService (“RADIUS”) server 342 may be used for caller authentication whena user of a mobile cellular device calls corporate network 340.

Generally, there can be four different cell sizes in a GSM network,referred to as macro, micro, pico, and umbrella cells. The coverage areaof each cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors. Onthe other hand, umbrella cells are used to cover shadowed regions ofsmaller cells and fill in gaps in coverage between those cells.

FIG. 4 illustrates an architecture of a typical GPRS network assegmented into four groups: users 450, radio access network 460, corenetwork 470, and interconnect network 480. In an example configurationthe wireless broadcast network 40 is encompassed by the radio accessnetwork 460, core network 470, and interconnect network 480. Users 450comprise a plurality of end users (though only mobile subscriber 455 isshown in FIG. 4). Radio access network 460 comprises a plurality of basestation subsystems such as BSSs 462, which include BTSs 464 and BSCs466. Core network 470 comprises a host of various network elements. Asillustrated here, core network 470 may comprise Mobile Switching Center(“MSC”) 471, Service Control Point (“SCP”) 472, gateway MSC 473, SGSN476, Home Location Register (“HLR”) 474, Authentication Center (“AuC”)475, Domain Name Server (“DNS”) 477, and GGSN 478. Interconnect network480 also comprises a host of various networks and other networkelements. As illustrated in FIG. 4, interconnect network 480 comprisesPublic Switched Telephone Network (“PSTN”) 482, Fixed-End System (“FES”)or Internet 484, firewall 488, and Corporate Network 489.

A mobile switching center can be connected to a large number of basestation controllers. At MSC 471, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (“PSTN”) 482 through Gateway MSC(“GMSC”) 473, and/or data may be sent to SGSN 476, which then sends thedata traffic to GGSN 478 for further forwarding.

When MSC 471 receives call traffic, for example, from BSC 466, it sendsa query to a database hosted by SCP 472. The SCP 472 processes therequest and issues a response to MSC 471 so that it may continue callprocessing as appropriate.

The HLR 474 is a centralized database for users to register to the GPRSnetwork. HLR 474 stores static information about the subscribers such asthe International Mobile Subscriber Identity (“IMSI”), subscribedservices, and a key for authenticating the subscriber. HLR 474 alsostores dynamic subscriber information such as the current location ofthe mobile subscriber. Associated with HLR 474 is AuC 475. AuC 475 is adatabase that contains the algorithms for authenticating subscribers andincludes the associated keys for encryption to safeguard the user inputfor authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as the devices 250 used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 4, whenmobile subscriber 455 initiates the attach process by turning on thenetwork capabilities of the mobile device, an attach request is sent bymobile subscriber 455 to SGSN 476. The SGSN 476 queries another SGSN, towhich mobile subscriber 455 was attached before, for the identity ofmobile subscriber 455. Upon receiving the identity of mobile subscriber455 from the other SGSN, SGSN 476 requests more information from mobilesubscriber 455. This information is used to authenticate mobilesubscriber 455 to SGSN 476 by HLR 474. Once verified, SGSN 476 sends alocation update to HLR 474 indicating the change of location to a newSGSN, in this case SGSN 476. HLR 474 notifies the old SGSN, to whichmobile subscriber 455 was attached before, to cancel the locationprocess for mobile subscriber 455. HLR 474 then notifies SGSN 476 thatthe location update has been performed. At this time, SGSN 476 sends anAttach Accept message to mobile subscriber 455, which in turn sends anAttach Complete message to SGSN 476.

After attaching itself with the network, mobile subscriber 455 then goesthrough the authentication process. In the authentication process, SGSN476 sends the authentication information to HLR 474, which sendsinformation back to SGSN 476 based on the user profile that was part ofthe user's initial setup. The SGSN 476 then sends a request forauthentication and ciphering to mobile subscriber 455. The mobilesubscriber 455 uses an algorithm to send the user identification (ID)and password to SGSN 476. The SGSN 476 uses the same algorithm andcompares the result. If a match occurs, SGSN 476 authenticates mobilesubscriber 455.

Next, the mobile subscriber 455 establishes a user session with thedestination network, corporate network 489, by going through a PacketData Protocol (“PDP”) activation process. Briefly, in the process,mobile subscriber 455 requests access to the Access Point Name (“APN”),for example, UPS.com (e.g., which can be corporate network 489 in FIG.4) and SGSN 476 receives the activation request from mobile subscriber455. SGSN 476 then initiates a Domain Name Service (“DNS”) query tolearn which GGSN node has access to the UPS.com APN. The DNS query issent to the DNS server within the core network 470, such as DNS 477,which is provisioned to map to one or more GGSN nodes in the corenetwork 470. Based on the APN, the mapped GGSN 478 can access therequested corporate network 489. The SGSN 476 then sends to GGSN 478 aCreate Packet Data Protocol (“PDP”) Context Request message thatcontains necessary information. The GGSN 478 sends a Create PDP ContextResponse message to SGSN 476, which then sends an Activate PDP ContextAccept message to mobile subscriber 455.

Once activated, data packets of the call made by mobile subscriber 455can then go through radio access network 460, core network 470, andinterconnect network 480, in a particular fixed-end system or Internet484 and firewall 488, to reach corporate network 489.

Thus, network elements that can invoke the functionality of providingemergency alert information based on subscriber location can include butare not limited to Gateway GPRS Support Node tables, Fixed End Systemrouter tables, firewall systems, VPN tunnels, and any number of othernetwork elements as required by the particular digital network.

FIG. 5 illustrates another exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture 500 in which providing emergency alertinformation based on subscriber location can be incorporated. In anexample embodiment, the wireless network 52 is encompassed by thenetwork architecture 500. As illustrated, architecture 500 of FIG. 5includes a GSM core network 501, a GPRS network 530 and an IP multimedianetwork 538. The GSM core network 501 includes a Mobile Station (MS)502, at least one Base Transceiver Station (BTS) 504 and a Base StationController (BSC) 506. The MS 502 is physical equipment or MobileEquipment (ME), such as a mobile phone or a laptop computer (e.g.,devices 50) that is used by mobile subscribers, with a Subscriberidentity Module (SIM). The SIM includes an International MobileSubscriber Identity (IMSI), which is a unique identifier of asubscriber. The BTS 504 is physical equipment, such as a radio tower,that enables a radio interface to communicate with the MS. Each BTS mayserve more than one MS. The BSC 506 manages radio resources, includingthe BTS. The BSC may be connected to several BTSs. The BSC and BTScomponents, in combination, are generally referred to as a base station(BSS) or radio access network (RAN) 503.

The GSM core network 501 also includes a Mobile Switching Center (MSC)508, a Gateway Mobile Switching Center (GMSC) 510, a Home LocationRegister (HLR) 512, Visitor Location Register (VLR) 514, anAuthentication Center (AuC) 518, and an Equipment Identity Register(EIR) 516. The MSC 508 performs a switching function for the network.The MSC also performs other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC510 provides a gateway between the GSM network and other networks, suchas an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 520. Thus, the GMSC 510 provides interworkingfunctionality with external networks.

The HLR 512 is a database that contains administrative informationregarding each subscriber registered in a corresponding GSM network. TheHLR 512 also contains the current location of each MS. The VLR 514 is adatabase that contains selected administrative information from the HLR512. The VLR contains information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 512 and the VLR 514,together with the MSC 508, provide the call routing and roamingcapabilities of GSM. The AuC 516 provides the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 518 storessecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 509 allows one-to-one ShortMessage Service (SMS) messages to be sent to/from the MS 502. A PushProxy Gateway (PPG) 511 is used to “push” (i.e., send without asynchronous request) content to the MS 502. The PPG 511 acts as a proxybetween wired and wireless networks to facilitate pushing of data to theMS 502. A Short Message Peer to Peer (SMPP) protocol router 513 isprovided to convert SMS-based SMPP messages to cell broadcast messages.SMPP is a protocol for exchanging SMS messages between SMS peer entitiessuch as short message service centers. The SMPP protocol is often usedto allow third parties, e.g., content suppliers such as newsorganizations, to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS first registers with the network to indicate itscurrent location by performing a location update and IMSI attachprocedure. The MS 502 sends a location update including its currentlocation information to the MSC/VLR, via the BTS 504 and the BSC 506.The location information is then sent to the MS's HLR. The HLR isupdated with the location information received from the MSC/VLR. Thelocation update also is performed when the MS moves to a new locationarea. Typically, the location update is periodically performed to updatethe database as location updating events occur.

The GPRS network 530 is logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 532, a cell broadcast and a GatewayGPRS support node (GGSN) 534. The SGSN 532 is at the same hierarchicallevel as the MSC 508 in the GSM network. The SGSN controls theconnection between the GPRS network and the MS 502. The SGSN also keepstrack of individual MS's locations and security functions and accesscontrols.

A Cell Broadcast Center (CBC) 533 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

The GGSN 534 provides a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 536. That is, the GGSNprovides interworking functionality with external networks, and sets upa logical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it is transferred to an external TCP-IP network536, such as an X.25 network or the Internet. In order to access GPRSservices, the MS first attaches itself to the GPRS network by performingan attach procedure. The MS then activates a packet data protocol (PDP)context, thus activating a packet communication session between the MS,the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services can be used inparallel. The MS can operate in one three classes: class A, class B, andclass C. A class A MS can attach to the network for both GPRS servicesand GSM services simultaneously. A class A MS also supports simultaneousoperation of GPRS services and GSM services. For example, class Amobiles can receive GSM voice/data/SMS calls and GPRS data calls at thesame time.

A class B MS can attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

A GPRS network 530 can be designed to operate in three network operationmodes (NOM1, NOM2 and NOM3). A network operation mode of a GPRS networkis indicated by a parameter in system information messages transmittedwithin a cell. The system information messages dictates a MS where tolisten for paging messages and how signal towards the network. Thenetwork operation mode represents the capabilities of the GPRS network.In a NOM1 network, a MS can receive pages from a circuit switched domain(voice call) when engaged in a data call. The MS can suspend the datacall or take both simultaneously, depending on the ability of the MS. Ina NOM2 network, a MS may not received pages from a circuit switcheddomain when engaged in a data call, since the MS is receiving data andis not listening to a paging channel In a NOM3 network, a MS can monitorpages for a circuit switched network while received data and vice versa.

The IP multimedia network 538 was introduced with 3GPP Release 5, andincludes an IP multimedia subsystem (IMS) 540 to provide rich multimediaservices to end users. A representative set of the network entitieswithin the IMS 540 are a call/session control function (CSCF), a mediagateway control function (MGCF) 546, a media gateway (MGW) 548, and amaster subscriber database, called a home subscriber server (HSS) 550.The HSS 550 may be common to the GSM network 501, the GPRS network 530as well as the IP multimedia network 538.

The IP multimedia system 540 is built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)543, a proxy CSCF (P-CSCF) 542, and a serving CSCF (S-CSCF) 544. TheP-CSCF 542 is the MS's first point of contact with the IMS 540. TheP-CSCF 542 forwards session initiation protocol (SIP) messages receivedfrom the MS to an SIP server in a home network (and vice versa) of theMS. The P-CSCF 542 may also modify an outgoing request according to aset of rules defined by the network operator (for example, addressanalysis and potential modification).

The I-CSCF 543, forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. The I-CSCF 543 may contact asubscriber location function (SLF) 545 to determine which HSS 550 to usefor the particular subscriber, if multiple HSS's 550 are present. TheS-CSCF 544 performs the session control services for the MS 502. Thisincludes routing originating sessions to external networks and routingterminating sessions to visited networks. The S-CSCF 544 also decideswhether an application server (AS) 552 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromthe HSS 550 (or other sources, such as an application server 552). TheAS 552 also communicates to a location server 556 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of the MS 502.

The HSS 550 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 550, a subscriber location function providesinformation on the HSS 550 that contains the profile of a givensubscriber.

The MGCF 546 provides interworking functionality between SIP sessioncontrol signaling from the IMS 540 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls the mediagateway (MGW) 548 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 548 alsocommunicates with other IP multimedia networks 554.

Push to Talk over Cellular (PoC) capable mobile phones register with thewireless network when the phones are in a predefined area (e.g., jobsite, etc.). When the mobile phones leave the area, they register withthe network in their new location as being outside the predefined area.This registration, however, does not indicate the actual physicallocation of the mobile phones outside the pre-defined area.

While example embodiments of providing emergency alert information basedon subscriber location has been described in connection with variouscomputing devices, the underlying concepts can be applied to anycomputing device or system capable of providing emergency alertinformation based on subscriber location. The various techniquesdescribed herein can be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and apparatus for providing emergency alert information based onsubscriber location, or certain aspects or portions thereof, can takethe form of program code (i.e., instructions) embodied in tangiblemedia, such as floppy diskettes, CD-ROMs, hard drives, or any othermachine-readable storage medium, wherein, when the program code isloaded into and executed by a machine, such as a computer, the machinebecomes an apparatus for providing emergency alert information based onsubscriber location. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile and non-volatile memory and/or storage elements), at least oneinput device, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. In any case,the language can be a compiled or interpreted language, and combinedwith hardware implementations.

The methods and apparatus for providing emergency alert informationbased on subscriber location also can be practiced via communicationsembodied in the form of program code that is transmitted over sometransmission medium, such as over electrical wiring or cabling, throughfiber optics, or via any other form of transmission, wherein, when theprogram code is received and loaded into and executed by a machine, suchas an EPROM, a gate array, a programmable logic device (PLD), a clientcomputer, or the like, the machine becomes an apparatus for providingemergency alert information based on subscriber location. Whenimplemented on a general-purpose processor, the program code combineswith the processor to provide a unique apparatus that operates to invokethe functionality of providing emergency alert information based onsubscriber location. Additionally, any storage techniques used inconnection with providing emergency alert information based onsubscriber location can invariably be a combination of hardware andsoftware.

While providing emergency alert information based on subscriber locationhas been described in connection with the various embodiments of thevarious figures, it is to be understood that other similar embodimentscan be used or modifications and additions can be made to the describedembodiment for performing the same function of providing emergency alertinformation based on subscriber location without deviating therefrom.For example, one skilled in the art will recognize that a system forproviding emergency alert information based on subscriber location asdescribed may apply to any environment, whether wired or wireless, andmay be applied to any number of devices connected via a communicationsnetwork and interacting across the network. Therefore, providingemergency alert information based on subscriber location should not belimited to any single embodiment, but rather should be construed inbreadth and scope in accordance with the appended claims.

What is claimed is:
 1. A method comprising: receiving, at an emergencyalert server, an indication of an emergency alert from an emergencyalert system; transmitting, from the emergency alert server to asupplemental emergency alert server, a request for multimedia contentassociated with the emergency alert, the request comprising anindication of a location of a wireless mobile device and an indicationof an emergency personnel status of a subscriber associated with thewireless mobile device, wherein the request causes the supplementalemergency alert server to determine the multimedia content associatedwith the emergency alert based on the indication of the location of thewireless mobile device and the indication of the emergency personnelstatus of the subscriber associated with the wireless mobile device;receiving, at the emergency alert server from the supplemental emergencyalert server, the multimedia content associated with the emergencyalert; and transmitting the multimedia content from the emergency alertserver to the wireless mobile device.
 2. The method of claim 1, furthercomprising retrieving the multimedia content from an external storagedevice.
 3. The method of claim 1, wherein the request further comprisesat least one of a type of emergency associated with the emergency alertor a capability of the wireless mobile device.
 4. The method of claim 3,wherein the request further causes the supplemental emergency alertserver to determine the multimedia content associated with the emergencyalert based on the type of emergency associated with the emergencyalert.
 5. The method of claim 3, wherein the request further causes thesupplemental emergency alert server to determine the multimedia contentassociated with the emergency alert based on the capability of thewireless mobile device.
 6. The method of claim 1, wherein the multimediacontent comprises at least one of a map, an evacuation route, atelephone number, an email address, or contact information of anemergency services provider.
 7. The method of claim 1, wherein themultimedia content is received at the emergency alert server via one ofan intranet or an internet.
 8. A system comprising: a memory comprisingcomputer instructions; and a processor coupled to the memory, wherein,when executing the computer instructions, the processor effectuatesoperations comprising: receiving an indication of an emergency alertfrom an emergency alert system; transmitting, to a supplementalemergency alert server, a request for multimedia content associated withthe emergency alert, the request comprising an indication of a locationof a wireless mobile device and an indication of an emergency personnelstatus of a subscriber associated with the wireless mobile device,wherein the request causes the supplemental emergency alert server todetermine the multimedia content associated with the emergency alertbased on the indication of the location of the wireless mobile deviceand the indication of the emergency personnel status of the subscriberassociated with the wireless mobile device; receiving, from thesupplemental emergency alert server, the multimedia content associatedwith the emergency alert; and transmitting the multimedia content to thewireless mobile device.
 9. The system of claim 8, wherein the operationsfurther comprise retrieving the multimedia content from an externalstorage device.
 10. The system of claim 8, wherein the request furthercomprises at least one of a type of emergency associated with theemergency alert or a capability of the wireless mobile device.
 11. Thesystem of claim 10, wherein the request further causes the supplementalemergency alert server to determine the multimedia content associatedwith the emergency alert based on the type of emergency associated withthe emergency alert.
 12. The system of claim 10, wherein the requestfurther causes the supplemental emergency alert server to determine themultimedia content associated with the emergency alert based on thecapability of the wireless mobile device.
 13. The system of claim 8,wherein the multimedia content comprises at least one of a map, anevacuation route, a telephone number, an email address, or contactinformation of an emergency services provider.
 14. The system of claim8, wherein the multimedia content is received via one of an intranet oran internet.
 15. A computer-readable medium that is not a transientsignal comprising computer-executable instructions, which when executedby a processor, cause the processor to effectuate operations comprising:receiving an indication of an emergency alert from an emergency alertsystem; transmitting, to a supplemental emergency alert server, arequest for multimedia content associated with the emergency alert, therequest comprising an indication of a location of a wireless mobiledevice and an indication of an emergency personnel status of asubscriber associated with the wireless mobile device, wherein therequest causes the supplemental emergency alert server to determine themultimedia content associated with the emergency alert based on theindication of the location of the wireless mobile device and theindication of the emergency personnel status of the subscriberassociated with the wireless mobile device; receiving, from thesupplemental emergency alert server, the multimedia content associatedwith the emergency alert; and transmitting the multimedia content to thewireless mobile device.
 16. The computer-readable medium of claim 15,wherein the operations further comprise retrieving the multimediacontent from an external storage device.
 17. The computer-readablemedium of claim 15, wherein the request further comprises at least oneof a type of emergency associated with the emergency alert or acapability of the wireless mobile device.
 18. The computer-readablemedium of claim 17, wherein the request causes the supplementalemergency alert server to determine the multimedia content associatedwith the emergency alert further based on the type of emergencyassociated with the emergency alert.
 19. The computer-readable medium ofclaim 17, wherein the request further causes the supplemental emergencyalert server to determine the multimedia content associated with theemergency alert based on the capability of the wireless mobile device.20. The computer-readable medium of claim 15, wherein the multimediacontent comprises at least one of a map, an evacuation route, atelephone number, an email address, or contact information of anemergency services provider.